d FN.Footnote*†‡§¶#*†‡§¶# \t —:;,.…!? 3_Z b IXIndex LOF Fg.Figure L.ListingTb.Table REFImported Graphics TOC H1.Heading1 H2.Heading2 H3.Heading3RH2.RoutineHd2RH3.RoutineHd3RoH.RoutineHeading "';),<person> <when
ColsFullWidth
ColsTextWidthEscGetTrackReferenceMLCv Multipage
ParamBlock
ResultList RoutineColsSumCols SumGlblVarsSumParam
SumResultListTbHTbHCTbHRTbTTbTR TblFullWidth TblTextWidthUNotecvegmov multicolumnobjepanoref“<““=”“|”AC AT AL AF A EquationVariables BOOK-COMPONENT BOOK-COMPONENT NoName BOOK-COMPONENT ÄÄ ` IÅ t ) ) ) ) ), )¬ 0≠ ;
<Ä * Z[ 0Δ &; &= (ä (åÄ@ 4ûÄ> 4üÄ? 4ìG %ùÄ ã ç é õ Ä’Ä ÄÚÄ ÄˆÄ Y è x/ ¥ (éÄe (êÄf ∑ #I Ø ≤
B39185: Fg.Figure: Figure2-2 Creating an image track for an object ~
337642: L.Listing: Listing2-2 Getting a node’s name %QuickTimeVR file format<$startrange> Ä
M11941: Fg.Figure: Figure2-3 The structure of a single-node object movie file Ä
O35064: Fg.Figure: Figure2-4 The structure of a single-node panorama movie file Ä
E23630: Fg.Figure: Figure2-5 The structure of a multi-node movie file u user data Ä user data w (QuickTimeVR movie controller:specifying Ä3 5QuickTimeVR file format:sample code for<$startrange> x
J35598: L.Listing: Listing2-1 Specifying the QuickTimeVR movie controller ÄA
:41128: H1.Heading1: 1 Using the Speech Recognition Manager Ä<
F16952: L.Listing: Listing2-2 Extracting a custom atom from a VR world ÉL $sample routines:<cv>MyGetPREFData<n> Ä% $sample routines:<cv>MyGetNodeName<n> ÄL frame animation:stored in files ÄM view states:stored in files ÄO (<cv>kQTVRWorldHeaderAtomType<n> constant ÄP *<cv>kQTVRImagingParentAtomType<n> constant ÄQ (<cv>kQTVRPanoImagingAtomType<n> constant ÄR '<cv>kQTVRNodeParentAtomType<n> constant ÄS #<cv>kQTVRNodeIDAtomType<n> constant ÄT )<cv>kQTVRNodeLocationAtomType<n> constant ÄU '<cv>kQTVRNodeHeaderAtomType<n> constant ÄV *<cv>kQTVRHotSpotParentAtomType<n> constant ÄW $<cv>kQTVRHotSpotAtomType<n> constant ÄX (<cv>kQTVRHotSpotInfoAtomType<n> constant ÄY %<cv>kQTVRLinkInfoAtomType<n> constant ÄZ #<cv>kQTVRStringAtomType<n> constant Ä[ +<cv>kQTVRPanoSampleDataAtomType<n> constant Ä\ '<cv>kQTVRAngleRangeAtomType<n> constant Ä] *<cv>kQTVRTrackRefArrayAtomType<n> constant Ä^ *<cv>kQTVRPanConstraintAtomType<n> constant Ä_ +<cv>kQTVRTiltConstraintAtomType<n> constant Ä` *<cv>kQTVRFOVConstraintAtomType<n> constant Äa &<cv>kQTVRImageTrackRefType<n> constant Ä1 #QuickTimeVR file format<$endrange> Äb (<cv>kQTVRHotSpotTrackRefType<n> constant Äc <cv>kQTVRValidPan<n> constant Äd <cv>kQTVRValidTilt<n> constant Äe <cv>kQTVRValidFOV<n> constant Äf $<cv>kQTVRValidViewCenter<n> constant Äg .<cv>kQTVRObjectAnimateViewFramesOn<n> constant Äh 1<cv>kQTVRObjectPalindromeViewFramesOn<n> constant Äi 0<cv>kQTVRObjectStartFirstViewFrameOn<n> constant Äj )<cv>kQTVRObjectAnimateViewsOn<n> constant Äk ,<cv>kQTVRObjectPalindromeViewsOn<n> constant Äl .<cv>kQTVRObjectSyncViewToFrameRate<n> constant " /<cv>kQTVRObjectDontLoopViewFramesOn<n> constant Än $<cv>kQTVRObjectWrapPanOn<n> constant Äo %<cv>kQTVRObjectWrapTiltOn<n> constant Äp $<cv>kQTVRObjectCanZoomOn<n> constant Äq ,<cv>kQTVRObjectReverseHControlOn<n> constant Är ,<cv>kQTVRObjectReverseVControlOn<n> constant Äs *<cv>kQTVRObjectSwapHVControlOn<n> constant Ät (<cv>kQTVRObjectTranslationOn<n> constant Äv !<cv>kQTControllerType<n> constant Å <cv>kQTControllerID<n> constant Äw "<cv>kGrabberScrollerUI<n> constant Äx <cv>kOldJoyStickUI<n> constant Äy <cv>kJoystickUI<n> constant Äz <cv>kGrabberUI<n> constant Ä{ <cv>kAbsoluteUI<n> constant Ä| <cv>kQTVRSameFile<n> constant Ä} '<cv>kQTVRPanoFlagHorizontal<n> constant Ä~ !<cv>QTVRSampleDescription<n> type Ä <cv>VRStringAtom<n> type Å <cv>VRWorldHeaderAtom<n> type Å <cv>VRPanoImagingAtom<n> type Å <cv>VRNodeLocationAtom<n> type Å <cv>VRNodeHeaderAtom<n> type Å <cv>VRHotSpotInfoAtom<n> type Å <cv>VRLinkHotSpotAtom<n> type Å <cv>VRAngleRangeAtom<n> type Å <cv>VRPanoSampleAtom<n> type Å <cv>VRObjectSampleAtom<n> type Å <cv>VRTrackRefEntry<n> type ÄN
538596: RH3.RoutineHd3: 3 Object Sample Atom Structure Äu
116823: RH3.RoutineHd3: 3 Link Hot Spot Valid Bits Å
515303: RH3.RoutineHd3: 3 Imaging Property Valid Flags Å $<cv>kQTVRValidCorrection<n> constant Å !<cv>kQTVRValidQuality<n> constant Å $<cv>kQTVRValidDirectDraw<n> constant Å ,<cv>kQTVRValidFirstExtraProperty<n> constant Å 3QuickTimeVR file format:sample code for<$endrange> Å! 1QuickTimeVR file format:constants for<$endrange> Å" 7QuickTimeVR file format:data structures for<$endrange> Å# QuickTimeVR file format:defined Å$ 3QuickTimeVR file format:for panoramas<$startrange> Å% 1QuickTimeVR file format:for panoramas<$endrange> Å& 1QuickTimeVR file format:for objects<$startrange> Å' /QuickTimeVR file format:for objects<$endrange> Å( nodes:getting name of Å) QTVR tracks:defined Å* VR worlds:defined Å+ "QTVR tracks:format of<$startrange> Å, QTVR tracks:format of<$endrange> Å- node information atom containers Å. 'panorama tracks, format of<$startrange> Å/ %panorama tracks, format of<$endrange> Å0 %object tracks, format of<$startrange> Å1 #object tracks, format of<$endrange> Å2 /QuickTimeVR movie files:format of<$startrange> Å3 -QuickTimeVR movie files:format of<$endrange> Å4 -panorama image tracks, format of<$startrange> Å5 +panorama image tracks, format of<$endrange> Å6 .panoramic images:storing in files<$startrange> Å7 ,panoramic images:storing in files<$endrange> Å8 dicing Å9 compressors:for panorama data Å: low-resolution image tracks Å; hot spot image tracks Å< %compressors:for hot spot image tracks Å= +object image tracks, format of<$startrange> Å> )object image tracks, format of<$endrange> Å? atom containers Å@ atoms ÅA /VR worlds:getting information from<$startrange> ÅB -VR worlds:getting information from<$endrange> Ä) ,nodes:getting information about<$startrange> ÅD *nodes:getting information about<$endrange> ÅE node header atoms ÅF VR world atoms, types of ÅG node information atoms #
`35517: T1.Text1: This chapter begins by briefly describing the QuickTimeVR file format. Then it ÅI track references, types of ÅJ "imaging properties:valid flags for ÅK #link hot spot atoms:valid flags for ÅL animation settings ÅM control settings ÅN (QuickTimeVR movie controller:subtype of ÅO object controllers ÅP #sample description header structure ÅQ string atoms ÅR <cv>VRStringAtom<n> data type ÅS VR world header atoms ÅT &<cv>QTVRSampleDescription<n> data type ÅU "<cv>VRWorldHeaderAtom<n> data type ÅV panorama imaging atoms ÅW "<cv>VRPanoImagingAtom<n> data type ÅX node location atoms ÅY #<cv>VRNodeLocationAtom<n> data type ÅZ node header atoms Å[ !<cv>VRNodeHeaderAtom<n> data type Å\ hot spot information atoms Å] "<cv>VRHotSpotInfoAtom<n> data type Å^ link hot spot atoms Å_ "<cv>VRLinkHotSpotAtom<n> data type Å` angle range atoms Åa !<cv>VRAngleRangeAtom<n> data type Åb panorama sample atoms Åc !<cv>VRPanoSampleAtom<n> data type Åd object sample atoms Åe #<cv>VRObjectSampleAtom<n> data type Åf track reference array atoms Åg <cv>VRTrackRefEntry<n> data type Åh animation settings:in files Åi control settings:in files ÅH view centers:in files Åj frame rates:in files Åk view rates:in files Ål field of view:in files Ån mouse-motion scale Åo object image arrays Åp view durations:in files Åq view states:stored in files G
q39587: Fd.FieldDesc: kQTVRObjectPlayEveryViewFrameOn If this bit is set, play every view frame regardless of play ! /<cv>kQTVRObjectPlayEveryViewFrameOn<n> constant %openObjectId qtvr_file_format:2 66846 Ç
D28028: Fg.Figure: Figure4-6 Structure of the VRWorld atom container Ä2
,24487: RH3.RoutineHd3: 4 VR World Atom Types Ç
M35018: Fg.Figure: Figure4-7 Structure of the node information atom container Ç
J28275: Fg.Figure: Figure4-8 Structure of a panorama sample atom container Ç
]15777: T1.Text1: QuickTimeVR version 2.0 requires the original panoramic image to be rotated Ç8
436809: H1.Heading1: 1 QuickTimeVR Manager Reference 7Ç +100323 Ç! -100323 Ç" =100323 Ç# +102382 Ç$ -102382 Ç% =102382 Ç& +111744 Ç' -111744 Ç( =111744 Ç) +109752 Ç* -109752 Ç+ =109752 Ç, +123751 Ç- -123751 Ç. =123751 Ç/ +115180 Ç0 -115180 Ç1 =115180 4 %openObjectId qtvr_file_format:2 69434 5 %openObjectId qtvr_file_format:2 74576 H %openObjectId qtvr_file_format:2 71880 J %openObjectId qtvr_file_format:2 73013 K %openObjectId qtvr_file_format:2 73019 L %openObjectId qtvr_file_format:2 73031 M %openObjectId qtvr_file_format:2 18686 N %openObjectId qtvr_file_format:2 72735 O %openObjectId qtvr_file_format:2 71499 U %openObjectId qtvr_file_format:2 71593 V %openObjectId qtvr_file_format:2 56311 W $openObjectId qtvr_file_format:2 8132 X %openObjectId qtvr_file_format:2 66686 f %openObjectId qtvr_file_format:2 66688 g %openObjectId qtvr_file_format:2 66690 } %openObjectId qtvr_file_format:2 66692 Ä %openObjectId qtvr_file_format:2 74180 Ä %openObjectId qtvr_file_format:2 70298 Ä* %openObjectId qtvr_file_format:2 72592 Ä+ %openObjectId qtvr_file_format:2 68545 Ä4 %openObjectId qtvr_file_format:2 66697 ÄJ %openObjectId qtvr_file_format:2 71310 ÄK %openObjectId qtvr_file_format:2 73204 Å %openObjectId qtvr_file_format:2 73206 Å %openObjectId qtvr_file_format:2 73274 Ç %openObjectId qtvr_file_format:2 66718 Ç2 %openObjectId qtvr_file_format:2 66596 Ç3 %openObjectId qtvr_file_format:2 66598 Ç4 %openObjectId qtvr_file_format:2 66600 Ç5 %openObjectId qtvr_file_format:2 66604 Ç6 %openObjectId qtvr_file_format:2 66606 Ç7 %openObjectId qtvr_file_format:2 69178 Ç9 %openObjectId qtvr_file_format:2 69198 Ç: %openObjectId qtvr_file_format:2 68839 Ç; %openObjectId qtvr_file_format:2 66627 Ç< %openObjectId qtvr_file_format:2 66629 Ç= %openObjectId qtvr_file_format:2 71186 ! " F * 4 7 9 : / 0 < B G eÄ 4◊Nh " D28028: Fg.Figure: Figure4-6 Structure of the VRWorld atom container 4◊Nh 422049: RH3.RoutineHd3: 1 Scene Header Atom Structure 4◊Nh 829275: RH3.RoutineHd3: 1 Panorama Imaging Atom Structure 4◊Nh " J35598: L.Listing: Listing2-1 Specifying the QuickTimeVR movie controller 4◊Nh 324430: RH3.RoutineHd3: 1 Node Header Atom Structure 4◊Nh 538591: RH3.RoutineHd3: 1 Node Location Atom Structure 4◊Nh .24345: RH3.RoutineHd3: 1 String Atom Structure 4◊Nh <18195: RH3.RoutineHd3: 1 Hot Spot Information Atom Structure 4◊Nh 722542: RH3.RoutineHd3: 1 Panorama Sample Atom Structure 4◊Nh %" C10226: Fg.Figure: Figure1-8 Creating an image track for a panorama 4◊Nh & 332544: RH3.RoutineHd3: 1 Angle Range Atom Structure 4◊Nh ' 332544: RH3.RoutineHd3: 1 Angle Range Atom Structure 4◊Nh ( 332544: RH3.RoutineHd3: 1 Angle Range Atom Structure 4◊Nh ) 332544: RH3.RoutineHd3: 1 Angle Range Atom Structure 4◊Nh , +26539: RH3.RoutineHd3: 1 Animation Settings 4◊Nh - )12277: RH3.RoutineHd3: 1 Control Settings 4◊Nh . 517065: RH3.RoutineHd3: 1 Link Hot Spot Atom Structure 4◊Nh H .22015: RH3.RoutineHd3: 3 Panorama Sample Flags 4◊Nh I) 722542: RH3.RoutineHd3: 1 Panorama Sample Atom Structure 4◊Nh 1 017700: RH3.RoutineHd3: 1 Object Controller Types 4◊Nh 3" B39185: Fg.Figure: Figure2-2 Creating an image track for an object 4◊Nh 5" M11941: Fg.Figure: Figure2-3 The structure of a single-node object movie file 4◊Nh 6" O35064: Fg.Figure: Figure2-4 The structure of a single-node panorama movie file 4◊Nh C 436809: H1.Heading1: 1 QuickTimeVR Manager Reference 4◊Nh 8" E23630: Fg.Figure: Figure2-5 The structure of a multi-node movie file 4◊Nh ; 336904: H2.Heading2: 2 Specifying a Movie Controller 4◊Nh J) 538591: RH3.RoutineHd3: 1 Node Location Atom Structure 4◊Nh 422049: RH3.RoutineHd3: 1 Scene Header Atom Structure 4◊Nh @" 337642: L.Listing: Listing2-2 Getting a node’s name 4◊Nh A" 337642: L.Listing: Listing2-2 Getting a node’s name 4◊Nh K 817698: RH3.RoutineHd3: 3 Track Reference Entry Structure 4◊Nh ,24487: RH3.RoutineHd3: 4 VR World Atom Types 4◊Nh ?" M35018: Fg.Figure: Figure4-7 Structure of the node information atom container 4◊Nh L) 517065: RH3.RoutineHd3: 1 Link Hot Spot Atom Structure 4◊Nh M .41833: RH3.RoutineHd3: 3 Track Reference Types 4◊Nh O) 538596: RH3.RoutineHd3: 3 Object Sample Atom Structure 4◊Nh P) 538596: RH3.RoutineHd3: 3 Object Sample Atom Structure 4◊Nh Q) 538596: RH3.RoutineHd3: 3 Object Sample Atom Structure 4◊Nh S 116823: RH3.RoutineHd3: 3 Link Hot Spot Valid Bits 4◊Nh T 116823: RH3.RoutineHd3: 3 Link Hot Spot Valid Bits 4◊Nh U) 829275: RH3.RoutineHd3: 1 Panorama Imaging Atom Structure 4◊Nh V 515303: RH3.RoutineHd3: 3 Imaging Property Valid Flags 4◊Nh =" F16952: L.Listing: Listing2-2 Extracting a custom atom from a VR world 4◊Nh D 324430: RH3.RoutineHd3: 1 Node Header Atom Structure 4◊Nh \" J28275: Fg.Figure: Figure4-8 Structure of a panorama sample atom container A <$lastpagenum> ;<$monthname> <$daynum>, <$year> <$hour>:<$minute00> <$ampm> <$year> ;<$monthname> <$daynum>, <$year> <$hour>:<$minute00> <$ampm> "<$monthnum>/<$daynum>/<$shortyear> <$monthname> <$daynum>, <$year> "<$monthnum>/<$daynum>/<$shortyear> <$fullfilename>
NOT USED Z<$paratext[H1.Heading1,CmH.CommHd,CmH0.CommHd0,H1.Multifile,CmH.Multifile,CmH0.Multifile]> 2notebat<8bat>u 2impbat<8bat>s Heading beg. on Page
htmlTopBanner"<!-- top image banner and para --> htmlBottomBanner%<!-- bottom image banner and para --> htmlButton5)<A HREF="<$parentdoc>">Section top</A> | htmlButton6<!--> htmlButton7<!--> htmlButton8<!-->
Ä A Å Å P HIDDEN ÄUÄU A ÄWÄW ÄYÄY VÄo A XX ÄgÄg ZZ P ÄiÄi Q A ÄkÄk P Ä&Ä& A Ä(Ä( Ä*Ä* Ä/Ä/ A ÄÄ ÄÄ A ÄÄ ÄnÄn Q A Ä3Ä3 Ä5Ä5 ÄsÄs Q A ÄvÄv Headings ÅHâb HTML ? ÇLR A V ÄŸX ÄıF Figure1 3 (á@ (Ëa (ã4 (ç5 (è5 (ë5 (ì5 ~ 4 3IÄÄ
Ä 4 (ï6 Ç 4 3’ÄÄ
Ñ 4 a ç- ·- 5dÄÄ
â 4 (ó6 (ô6 û 4 ±0 ∂1 ª1 ¿1 ≈1 1 $# 4 - & 4 P ( 4 6^ÄÄ
4 ÄÄ
a ÿ @ 6°ÄÄ
, 4 )a (õ4 6ÌÄÄ
4®ÄÄ
. 4 Ê- 2⁄ÄÄ
¶- (ù5 Á 4 4KÄÄ
9 ÄÄ
ºa ›- ‚. X- Y- Z- #HG : 4 åa Ä- =3 8"ÄÄ
¬a 5ΩÄÄ
…a )
€- )
)= )
) I $˘- %øa $˙- Ä⁄i Ä€j Ä‹ 1. ĢC
Listing 1
— Ä˙a C 4 (ü5 y TeI #ø- E 4 (°5 Ä›l 2. Äfil 3. (£4 (•7 6 ÄÄ
qÜ™™¿Ò*ö d3The string usage. Currently, this field is unused.
ãd ¡Ô estringLength ¢
sÜ™™¡™ô d%The length, in bytes, of the string.
ãe ¡ Ó etheString ¢
Ä Ü™™¡/™ò dGThe string. The string atom structure is extended to hold this string.
"¡>*ó l$ Q VR World Header Atom Structure
1C¡J*ñ ,g A VR world header atom contains the name of the scene and the default node ID to be used when the qfile is first opened. The structure of a VR world header atom is defined by the ãVRWorldHeaderAtom Ü data Ltype: , Å
ÄÜ™™¿n™£ ,n The atom is a VR world header atom. See S “VR World Header Atom Structure” R for the structure of this ¿z™¢ Etype of atom.
ã( ¿äˇ˜ m% ¸ kQTVRImagingParentAtomType ¢
ÄÜ™™¿ö™° $_ The atom is an imaging parent atom, which contains one or more imaging atoms. An imaging atom 0¿¶™† Qdescribes the default imaging characteristics for one type of node in thescene. LCurrently, QuickTimeVR supports two types ofimaging atoms: object-imaging D"atoms and panorama-imaging atoms.
ã) ¿ŒˇÛ m# ˝ kQTVRPanoImagingAtomType ¢
|Ü™™¿fi™ù ,l The atom is a panorama-imaging atom. See Y “Panorama-Imaging Atom Structure” Z , for the structure of ¿Í™ú Dthis type of atom.
ã* ¿˙ˇÒ e kQTVRObjectImagingAtomType ¢
~Ü™™¡
™õ d& The atom is an object-imaging atom.
ã+ ¡ˇ e kQTVRObjectImagingAtomType ¢
ÄIÜ™™¡*™ö l ÿ
ã, ¡:ˇÔ m" ˛ kQTVRNodeParentAtomType ¢
ÄÜ™™¡J™ô $f The atom is a node parent atom, which contains one or more node ID atoms that specify the IDs of all ¡V™ò Dthe nodes in the scene.
ã- ¡fˇÌ m ˇ kQTVRNodeIDAtomType ¢
ÄÜ™™¡v™ó $e The atom is a node ID atom, which specifies the node ID of a single node in the scene. Each node ID ¡Ç™ñ D8atom has a single child, which is a node location atom.
ã. ¡íˇÎ m$ kQTVRNodeLocationAtomType ¢
Ä Ü™™¡¢™ï ,o The atom is a node location atom. See d “Node Location Atom Structure” e for the structure of this type ¡Æ™î E of atom.
¡Ω™ì d Node Information Atom Types
qE¡…™í ,g s QuickTimeVR defines a number of types of atoms that can be contained in a node information atom. DEYou can use these constants to specify a node information atom type:
GÜ™™¿Ü™ú ,o The atom is a node header atom. See h “Node Header Atom Structure” k , for the structure of this type of ¿í™õ Eatom.
ã0 ¿¢ˇ m% kQTVRHotSpotParentAtomType ¢
fÜ™™¿≤™ö dc The atom is a hot spot parent atom, which contains one or more hot spot atoms and their children.
ã1 ¿¬ˇÔ m kQTVRHotSpotAtomType ¢
Ä Ü™™¿“™ô $g The atom is a hot spot atom. The atom ID is the same as the hot spot ID. A hot spot atom contains two 0¿fi™ò Qchildren: a hot spot information atom (which specifies general information about Rthe hot spot) and another atom (which contains specific information about the hot Dspot).
ã2 ¡ˇÎ m# kQTVRHotSpotInfoAtomType ¢
Å;Ü™™¡™ï ,g The atom is a hot spot information atom. See n “Hot Spot Information Atom Structure” o , for the ¡"™î E structure of this type of atom.
ã3 ¡2ˇÈ m kQTVRLinkInfoAtomType ¢
Å<Ü™™¡B™ì ,s The atom is a link hot spot atom. See û “Link Hot Spot Atom Structure” ù , for the structure of this type of ¡N™í Eatom.
¡]™ë dMiscellaneous Atom Types
1c¡i™ê $bQuickTimeVR defines a number of other types of atoms that can be contained in an atom container. D@You can use these constants to specify one of these atomtypes:
ÅFÜ™™¿…™£ $g The atom is a pan constraint atom, which contains information about the initial pan angle constraints 0¿’™¢ [for a panorama. See â “Angle Range Atom Structure” à , for the structure of this type E of atom.
ã9 ¿Òˇˆ m& kQTVRTiltConstraintAtomType ¢
ÅGÜ™™¡™† $i The atom is a tilt constraint atom, which contains information about the initial tilt angle constraints 0¡
™ü [for a panorama. See ã “Angle Range Atom Structure” å , for the structure of this type E of atom.
ã: ¡)ˇÛ m% kQTVRFOVConstraintAtomType ¢
ÅHÜ™™¡9™ù $d The atom is a field-of-view constraint atom, which contains information about the initial vertical 0¡E™ú Zfield-of-view constraints for a panorama. See ç “Angle Range Atom Structure” é , for E$the structure of this type of atom.
¡`™ö l Û Track Reference Types
Å=Ä¡l™ô ,l u QuickTimeVR defines several track reference types. You can use these constants Üas values for the krefType Ü parameter to the ãAddTrackReference Ü function (or other Movie Toolbox track reference D functions):
1Ä ¿A™ß ,y v The ãimagingValidFlags Ü field in a panorama-imaging atom structure D (link) E specifies which imaging Dlproperty fields in that structure are valid. You can use these bit flags to specify a value for that field:
ÄÜ™™¿Ÿ™ô dU If this bit is set, the ãcorrection Ü field holds a default correction mode.
ã> ¿ÈˇÓ m J kQTVRValidQuality ¢
ÄEÜ™™¿˘™ò dQIf this bit is set, the ãquality Ü field holds a default imaging quality.
ã? ¡ ˇÌ m K kQTVRValidDirectDraw ¢
ÄFÜ™™¡™ó dZ If this bit is set, the ãdirectDraw Ü field holds a default direct draw property.
ã@ ¡)ˇÏ m' L kQTVRValidFirstExtraProperty ¢
ÄGÜ™™¡9™ñ $u If this bit is set, the first element in the array in the ãimagingProperties Ü field holds a default imaging ¡E™ï D
property.
l¡T™î l ! Link Hot Spot Valid Bits
1Ç¡`™ì ,Ä w The ãtoValidFlags Ü field in a link hot spot atom structure Ú (link) Ò specifies which view settings are to be gused when moving to a destination node from a hot spot. You can use these bit flags to specify a value Dfor that field:
Ü™™¿e™® d;If this bit is set, the destination field of view is used.
ãD ¿uˇ˝ m kQTVRValidViewCenter ¢
ÄÜ™™¿Ö™ß d: If this bit is set, the destination view center is used.
Ŀ l [ Animation Settings
1ÅI¿†™• ,Ä x The ãanimationSettings Ü field of the object sample atom 7 (link) 6 is a long integer that specifies a set of hanimation settings for an object node. Animation settings specify characteristics of the movie while it DGis playing. You can use these constants to specify animation settings:
Ü™™¿C™® $g If this bit is set, synchronize the view animation to the frame animation and use the same options as ¿O™ß Dfor frame animation.
ãK ¿_ˇ¸ m* N kQTVRObjectDontLoopViewFramesOn ¢
LÜ™™¿o™¶ dV If this bit is set, stop playing the frame animation in the current view at the end.
ãLq¿ˇ˚ m/ L M kQTVRObjectPlayEveryViewFrameOn ¢
NÜ™™¿è™• $i If this bit is set, play every view frame regardless of play rate. The play rate is used to adjust the 0¿õ™§ Pduration in which a frame appears but no frames are skipped so the rate is not Dexact.
ÅS¿∂™¢ l ò Control Settings
ÅTÄ¿¬™° ,Ä y The
controlSettings
field of the object sample atom 9 (link) : is a long integer
that specifies a set of control Ä jsettings for an object node. Control settings specify Üwhether the object can wrap during panning and Djtilting, as well as other features of the node. The control settings are specified using these bit flags:
ÅeÜ™™¡j™å $LSee the section handlink “QuickTimeVR Manager/Control Settgins” for a more ¡v™ã LFcomplete description of these control settings. ë ˆs Ü ê
ÅQÄ¡éˇ‡ dConstant descriptions
ãM ¡ûˇ‡ m kQTVRObjectWrapPanOn ¢
Å]Ü™™¡Æ™ä $h If this bit is set, enable wrapping during panning. When this control setting is enabled, the user can 0¡∫™â Ewrap around from the current pan constraint maximum value to the pan DHconstraint minimum value (or vice versa) using the mouse or arrow keys.
Å_Ü™™æ™ß $k If this bit is set, enable zooming. When this control setting is enabled, the user can change the current 0¿J™¶ Pfield of view using the zoom-in and zoom-out keys on the keyboard (or using the DVR controller buttons).
ãP ¿fˇ˙ m' kQTVRObjectReverseHControlOn ¢
ÅaÜ™™¿v™§ dF If this bit is set, reverse the direction of the horizontal control.
ãQ ¿Üˇ˘ m' kQTVRObjectReverseVControlOn ¢
ÅbÜ™™¿ñ™£ dD If this bit is set, reverse the direction of the vertical control.
ãR ¿¶ˇ¯ m% kQTVRObjectSwapHVControlOn ¢
ÅcÜ™™¿∂™¢ dD If this bit is set, exchange the horizontal and vertical controls.
ãS ¿Δˇ˜ m# kQTVRObjectTranslationOn ¢
ÅdÜ™™¿÷™° $h If this bit is set, enable translation. When this setting is enabled, the user can translate using the 0¿‚™† Omouse when either the translate key is held down or the controller translation Dmode button is toggled on.
¿˝™û dController Subtype and ID
1ÅJ¡ ™ù ,i z A QuickTimeVR movie must contain a user data item that indicates which movie controller to use for hthe movie. The movie controller for QuickTimeVR movies has the controller type ãkQTVRQTVRType Ü DT(defined in ãQuickTime.h Ü) and a subtype and ID defined by these constants:
ÅgÜ™™¡ï™í d6The movie controller subtype for QuickTimeVR movies.
ãU ¡•ˇÁ m < kQTControllerID ¢
ÅhÜ™™¡µ™ë d1The movie controller ID for QuickTimeVR movies.
Ç#¡ƒ™ê l • Object Controller Types
qÇ&¡–™è ,Ä { The ãmovieType Ü field of the object sample atom structure ; (link) 8 specifies an object controller type, that is, gthe user interface to be used to manipulate the object. QuickTimeVR supports the following controller Dtypes:
Ä1Ü™™¿Ü™ú $bThe default controller, which displays a hand for dragging and rotation arrows when the cursor is ¿í™õ D&along the edges of the object window.
ãW ¿¢ˇ m $ kOldJoyStickUI ¢
ÅAÜ™™¿≤™ö $cA joystick controller, which displays a joystick-like interface for spinning the object. With this ¿æ™ô DTcontroller, the direction of panning is reversed from the direction of thegrabber.
ãX ¿ŒˇÓ m % kJoystickUI ¢
ÅBÜ™™¿fi™ò $cA joystick controller, which displays a joystick-like interface for spinning the object. With this ¿Í™ó DVcontroller, the direction of panning is consistent with the direction of thegrabber.
ãY ¿˙ˇÏ m & kGrabberUI ¢
2Ü™™¡
™ñ $lA grabber-only interface, which displays a hand for dragging but does ônot Ü display rotation arrows ¡™ï D9when the cursor is along the edges of the object window.
ãZ ¡&ˇÍ m ' kAbsoluteUI ¢
Ç)Ü™™¡6™î $eAn absolute controller, which displays a finger for pointing. The absolute controller switches views ¡B™ì D>based on a row-and-column grid mapped into the object window.
Ç¡Q™í dNode Location Flag
1ÇK¡]™ë ,zThe ãlocationFlags Ü field in the node location atom structure Ô (link) Ó indicates the location of the node idata relative to the file containing the node location atom. You can use this constant to specify a node D
location:
Ç( ÖUT¡åU8 %enum { 0¡òU6 4kQTVRSameFile= 0 E};
ÇNÄ¡Ωˇfi dConstant description
ã[ ¡Õˇfi m ( kQTVRSameFile ¢
WÇOÜ™™¡›™à d-The node is to be found in the current file.
6U¬ ¡Ô k 6U¬ ¡Ô %!!Y l ¬X ¬ë l %%" 9U¬ ¡Ô m # 9U¬ ¡Ô ¡Ë⁄ D! ! % ÇCÜ™™Ü™™ l Ë Panorama Sample Flag
field in the panorama sample atom structure Ï (link) Î specifies any Üspecial settings for the D7panorama. The flags are specified using this bit flag:
ÇI ÖUTµUQ %enum { 0¿AUO 9kQTVRPanoFlagHorizontal= 1 << 0 E};
ÇÄ¿fˇ˜ dConstant description
ã\ ¿vˇ˜ m" ) kQTVRPanoFlagHorizontal ¢
Ç*Ü™™¿Ü™° lN If this bit is set, the diced panoramic image is oriented horizontally. M
ÇM¿ï™† l õ Data Structures
j¿†™ü ,m - This section describes the data structures that you can use to access the information in the atoms in a ¿¨™û DQuickTimeVR movie.
¿æ™ù d$Sample Description Header Structure
1Ä¿ ™ú ,b | A VR world contains general information about a QuickTimeVR movie. For instance, a VR world _contains the ID of every node in the scene. A VR world is contained in the QTVR track’s sample L]description header, defined by the ãQTVRSampleDescription Ü data type: ã * Ä
Ä Ü™™¿E*® $OThe imaging mode to which the default values apply. See handlink “QuickTimeVR 0¿Q*ß KManager/Imaging Modes” for a description of the available imaging modes. A NVR world can contain more than one panorama-imaging atom if static and motion DHmodes are assigned different default values for any imaging properties.
ãp ¿xˇ˙ eimagingValidFlags ¢
Ä
Ü™™¿à*§ ,jA set of flags that indicate which imaging property fields in this structure are valid. See G “Imaging ¿î*£ LEProperty Valid Flags” F for a description of the available flags.
ãqq¿£ˇ¯ ecorrection ¢
Ä)Ü™™¿≥*¢ $_The default correction mode for panoramic nodes. See handlink “QuickTimeVR Manager/Correction ¿ø*° D<Modes” for a description of the available correction modes.
ãsq¿Œˇˆ e
quality ¢
Ä*Ü™™¿fi*† $\The default imaging quality for panoramic nodes. See handlink “QuickTimeVR Manager/Quality ¿Í*ü DBProperties” for a description of the available imaging qualities.
ãt ¿˘ˇÙ edirectDraw ¢
Ä+Ü™™¡ *û $QThe default direct draw property for panoramic nodes. See handlink “QuickTimeVR 0¡*ù OManager/Imaging Property Types” for a description of the available direct draw Dproperty values.
ãu ¡0ˇÒ eimagingProperties ¢
Ä-Ü™™¡@*õ d1Reserved for future panorama-imaging properties.
ãv ¡Oˇ ereserved1 ¢
Ä.Ü™™¡_*ö d Reserved. This field must be 0.
ãw ¡nˇÔ ereserved2 ¢
Ä/Ü™™¡~*ô d Reserved. This field must be 0.
*¡å™ò l" ^ Node Location Atom Structure
ÅoÄ¡ò™ó ,t Ö Ñ A node location atom describes the type of a node and its location. The structure Üof a node location LDatom is defined by the ãVRNodeLocationAtom Ü data type: .
Ä#Ü™™¿^™® $dThe ID of the string atom that contains the name of the scene. This atom should be a sibling of the ¿j™ß DHscene header atom. The value of this field is 0 if no name atom exists.
ãi ¿zˇ¸ edefaultNodeID ¢
Ä$Ü™™¿ä™¶ d^The ID of the default node (that is, the node to be displayed when the file is first opened).
ãjq¿öˇ˚ evrWorldFlags ¢
!Ü™™¿™™• dBA set of flags for the VR world. Currently, this field isunused.
ãk ¿∫ˇ˙ ereserved1 ¢
Ä%Ü™™¿ ™§ d Reserved. This field must be 0.
ãl ¿⁄ˇ˘ ereserved2 ¢
Ä&Ü™™¿Í™£ d Reserved. This field must be 0.
$¿˘™¢ l% T Panorama-Imaging Atom Structure
1Å¡™° ,l Ç É A panorama-imaging atom describes the default imaging characteristics for all the panoramic nodes _in a scene. In addition, if contained in a node atom, a panorama-imaging atom contains default fsettings for a particular panoramic node (which override the scene-wide defaults). The structure of a LYpanorama-imaging atom is defined by the ãVRPanoImagingAtom Ü data type: ã -
ÅÜ™™≤™® d, The index of the hot spot track reference.
å, ¿Bˇ˝ e minPan ¢
Å Ü™™¿R™ß d`The minimum pan angle, in degrees. For a full panorama, the value of this field is usually 0.0.
å- ¿bˇ¸ e maxPan ¢
Å
Ü™™¿r™¶ dbThe maximum pan angle, in degrees. For a full panorama, the value of this field is usually 360.0.
å. ¿Çˇ˚ e
minTilt ¢
ÅÜ™™¿í™• $fThe minimum tilt angle, in degrees. For a high-resolution panorama, a typical value for this field is ¿û™§ D–42.5.
å/ ¿Æˇ˘ e
maxTilt ¢
ÅÜ™™¿æ™£ $fThe maximum tilt angle, in degrees. For a high-resolution panorama, a typical value for this field is ¿ ™¢ D+42.5.
å0 ¿⁄ˇ˜ eminFieldOfView ¢
ÅÜ™™¿Í™° $dThe minimum vertical field of view, in degrees. For a high-resolution panorama, a typical value for ¿ˆ™† DWthis field is 5.0. The value in this field is 0 for the default minimum field of view.
å1 ¡ˇı emaxFieldOfView ¢
ÅÜ™™¡™ü $dThe maximum vertical field of view, in degrees. For a high-resolution panorama, a typical value for ¡"™û DXthis field is 85.0. The value in this field is 0 for the default maximum field of view.
å2 ¡2ˇÛ edefaultPan ¢
ÅÜ™™¡B™ù d#The default pan angle, in degrees.
å3 ¡RˇÚ edefaultTilt ¢
ÅÜ™™¡b™ú d$The default tilt angle, in degrees.
å4 ¡rˇÒ edefaultFieldOfView ¢
ÅÜ™™¡Ç™õ d1 The default vertical field of view, in degrees.
å5 ¡íˇ eimageSizeX ¢
ÅÜ™™¡¢™ö $ZThe width, in pixels, of the panorama stored in the highest resolution image track. For a ¡Æ™ô DAhigh-resolution panorama, a typical value for this field is 768.
å6 ¡æˇÓ eimageSizeY ¢
ÅÜ™™¡Œ™ò $[The height, in pixels, of the panorama stored in the highest resolution image track. For a ¡⁄™ó DBhigh-resolution panorama, a typical value for this field is 2496.
Ä4Ü™™¿Z™¢ d-The major version number of the file format.
ãy ¿jˇ˜ eminorVersion ¢
Ä5Ü™™¿z™° d-The minor version number of the file format.
ãz ¿äˇˆ enodeType ¢
Ä6Ü™™¿ö™† $aThe node type. See handlink “QuickTimeVR Manager/Node Types” for a description of the available ¿¶™ü Wnode types. Currently, this field should contain either ãkQTVRPanoramaType Ü or DkQTVRObjectType Ü.
ã{¿¬ˇÛ elocationFlags ¢
Ä7Ü™™¿“™ù $sThe location flags. Currently, this field must contain the value ãkQTVRSameFile Ü, indicating that the node ¿fi™ú D$is to be found in the current file.
ã| ¿ÓˇÒ elocationData ¢
Ä8Ü™™¿˛™õ $zThe location of the node data. When the ãlocationFlags Ü field is ãkQTVRSameFile Ü, this field should be 0. 0¡
™ö RThe nodes are found in the file in the same order that they are found in the node Dlist.
ã} ¡&ˇÓ ereserved1 ¢
Ä9Ü™™¡6™ò d Reserved. This field must be 0.
ã~ ¡FˇÌ ereserved2 ¢
Ä:Ü™™¡V™ó d Reserved. This field must be 0.
/¡e™ñ l b Node Header Atom Structure
1Åq¡q™ï ,o á Ü A node header atom describes the type and ID of a node, as well as other information about the node. LaThe structure of a node header atom is defined by the ãVRNodeHeaderAtom Ü data type: /
Ä;Ü™™¿N™§ d-The major version number of the file format.
å ¿^ˇ˘ eminorVersion ¢
Ä<Ü™™¿n™£ d-The minor version number of the file format.
å ¿~ˇ¯ enodeType ¢
Ä=Ü™™¿é™¢ $aThe node type. See handlink “QuickTimeVR Manager/Node Types” for a description of the available ¿ö™° \node types. Currently, this field
should contain either
kQTVRPanoramaType
or Ä DkQTVRObjectType
.
å ¿∂ˇı e nodeID ¢
Ä>Ü™™¿Δ™ü d
The node ID.
å ¿÷ˇÙ enameAtomID ¢
ÇÜ™™¿Ê™û $cThe ID of the string atom that contains the name of the node. This atom should be a sibling of the ¿Ú™ù DGnode header atom. The value of this field is 0 if no name atom exists.
å ¡ˇÚ ecommentAtomID ¢
Ä@Ü™™¡™ú $eThe ID of the string atom that contains a comment for the node. This atom should be a sibling of the ¡ ™õ DJnode header atom. The value of this field is 0 if no comment atom exists.
å ¡.ˇ ereserved1 ¢
ÄAÜ™™¡>™ö d Reserved. This field must be 0.
å ¡NˇÔ ereserved2 ¢
0Ü™™¡^™ô d Reserved. This field must be 0.
>¡m™ò l) ~ Hot Spot Information Atom Structure
?¡y™ó ,v â à A hot spot information atom contains general information about a hot spot. ˜The structure of a hot spot w LYinformation atom is defined by the ¯VRHotSpotInfoAtom ˜ Üdata type: ã 0
AÜ™™¿ñ™ò d-The major version number of the file format.
å ¿¶ˇÌ eminorVersion ¢
Ä?Ü™™¿∂™ó d-The minor version number of the file format.
å ¿ΔˇÏ ehotSpotType ¢
ÄXÜ™™¿÷™ñ $_The hot spot type. See handlink “QuickTimeVR Manager/Hot Spot Types” for a description of the ¿‚™ï Dpredefined hot spot types.
å
¿ÚˇÍ enameAtomID ¢
ÄYÜ™™¡™î $gThe ID of the string atom that contains the name of the hot spot. This atom should be a sibling of the ¡™ì DDhot spot atom. The value of this field is 0 if no name atom exists.
å ¡ ˇË ecommentAtomID ¢
ÄZÜ™™¡.™í $eThe ID of the string atom that contains a comment for the hot spot. This atom should be a sibling of ¡:™ë DKthe hot spot atom. The value of this field is 0 if no comment atom exists.
å q¡JˇÊ ecursorID ¢
Ä[Ü™™¡Z™ê $gAn array of three IDs for custom hot spot cursors (that is, cursors that override the default hot spot 0¡f™è Vcursors provided by QuickTimeVR). The first ID ( ãcursorID[0] Ü) specifies the [cursor that is displayed when it is in the hot spot. The second ID ( ãcursorID[1] Ü) Pspecifies the cursor that is displayed when it is in the hot spot and the mouse \button is down. The third ID ( ãcursorID[2] Ü) specifies the cursor that is displayed Swhen it is in the hot spot and the mouse button is released. To retain the default DJcursor for any of these operations, set the corresponding cursor ID to 0.
å
¡≤ˇfl e
bestPan ¢
Ä\Ü™™¡¬™â d.The best pan angle for viewing this hot spot.
å ¡“ˇfi ebestTilt ¢
WÄ^Ü™™¡‚™à d/The best tilt angle for viewing this hot spot.
9U¬ ¡Ô 5 9U¬ ¡Ô 4:66Y
l ¬X ¬ë Ç ::) 6U¬ ¡Ô É 8 6U¬ ¡Ô ¡€ˇ– D# # : å e
bestFOV ¢
Ä_Ü™™ó™™ d2The best field of view for viewing this hot spot.
Ä`Ü™™¿W™® $dThe bounding box for this hot spot, specified as the number of pixels in full panoramic space. This ¿c™ß D)field is valid only for panoramic nodes.
å ¿sˇ¸ e flags ¢
ÄeÜ™™¿É™¶ d:A set of hot spot flags. Currently, this field is unused.
å ¿ìˇ˚ ereserved1 ¢
ÄfÜ™™¿£™• d Reserved. This field must be 0.
å ¿≥ˇ˙ ereserved2 ¢
ÄgÜ™™¿√™§ d Reserved. This field must be 0.
Äh¿“™£ l" ú Link Hot Spot Atom Structure
1Äa¿fi™¢ ,p ã ä A link hot spot atom contains specific information about a link hot spot. The structure of a link hot LHspot atom is defined by the ãVRLinkHotSpotAtom Ü data type: 1
ÄmÜ™™¿^™® dUThe ID of the destination node (that is, the node to which this hot spot is linked).
å ¿nˇ˝ efromValidFlags ¢
ÄnÜ™™¿~™ß ,qA set of flags that indicate which source node view settings are valid. See @ “Link Hot Spot Valid Bits” ? ¿ä™¶ E*for a description of the available flags.
å ¿öˇ˚ e
fromPan ¢
ÄoÜ™™¿™™• dVThe current pan angle at the source node (that is, the node containing the hot spot).
å ¿∫ˇ˙ efromTilt ¢
ÄpÜ™™¿ ™§ d+The current tilt angle at the source node.
å ¿⁄ˇ˘ e
fromFOV ¢
@Ü™™¿Í™£ d.The current field of view at the source node.
å ¿˙ˇ¯ efromViewCenter ¢
ÄqÜ™™¡
™¢ d,The current view center at the source node.
å ¡ˇ˜ etoValidFlags ¢
ÄrÜ™™¡*™° ,kA set of flags that indicate which destination node view settings are valid. See B “Link Hot Spot Valid ¡6™† M5Bits” C for a description of the available flags.
å ¡Fˇı e toPan ¢
ÄtÜ™™¡V™ü d;The pan angle to use when displaying the destination node.
å ¡fˇÙ e toTilt ¢
ÄuÜ™™¡v™û d<The tilt angle to use when displaying the destination node.
å ¡ÜˇÛ e toFOV ¢
:Ü™™¡ñ™ù d?The field of view to use when displaying the destination node.
å! ¡¶ˇÚ etoViewCenter ¢
;Ü™™¡∂™ú d=The view center to use when displaying the destination node.
å" ¡ΔˇÒ edistance ¢
<Ü™™¡÷™õ d?The distance between the source node and the destination node.
Wå# ¡Êˇ e flags ¢
9U¬ ¡Ô Æ ; 9U¬ ¡Ô :@<<Y
l ¬X ¬ë Í @@+ 6U¬ ¡Ô Î > 6U¬ ¡Ô ¡fl™ê D ÅÅÅ @" ÄzÜ™™Ü™™ d?A set of link hot spot flags. Currently, this field is unused.
1Ås¿a™¶ ,h ç å An angle range atom specifies the minimum and maximum allowable angles for some viewing limit jor constraint. For example, the field-of-view constraint ìatom, the pan constraint atom, and the tilt mconstraint atom all specify constraints Üusing an angle range atom. The structure of an angle range atom L=is defined by the ãVRAngleRangeAtom Ü data type: 2
ÄCÜ™™¿Ò™ö d,The minimum angle in the range, in degrees.
å' ¡ˇÔ emaximumAngle ¢
ÄDÜ™™¡™ô d,The maximum angle in the range, in degrees.
U¡ ™ò l$ q Panorama Sample Atom Structure
Ç¡,™ó ,k è é A panorama sample atom describes a single panorama, including information ìabout the default " zviewing angles and the source panoramic image. ì ì Ω Figure4-8 º is a d ìiagram of a panorama sample atom D container.
WÅu¡hˇÍ lC ª Structure of a óp óanorama sample atom container µ
6U¬ ¡Ô Ì > 6U¬ ¡Ô =C??Y l ¬X ¬ë ; CC, 9U¬ ¡Ô < A 9U¬ ¡Ô ¡Ìˇƒ D% % C# ÅlÜ™™Ü™™ lt € ìThe structure Üof a panorama sample atom is defined by the ãVRPanoSampleAtom Ü data type: 3
ÅÜ™™¡z™u d-The major version number of the file format.
å) ¡äˇ eminorVersion ¢
ÅÜ™™¡ö™t d-The minor version number of the file format.
å* ¡™ˇ… eimageRefTrackIndex ¢
ÅÜ™™¡∫™s $oThe index of the image track reference. This is the index returned by the ãAddTrackReference Ü function 0¡Δ™r Qwhen the image track is added as a reference to the panorama track. There can be Mmore than one image track for a given
panorama track and hence multiple Ä Ureferences. (A panorama Ütrack might have multiple image tracks if the panoramas B Rhave different characteristics, which could occur if the panoramas were shot with 9U¬ ¡Ô > A 9U¬ ¡Ô @.BBY
Å"Ü™™¡ ™Ñ d-The major version number of the file format.
åA ¡ ˇŸ eminorVersion ¢
Å#Ü™™¡,*É d-The minor version number of the file format.
åB ¡;ˇÿ emovieType ¢
Å$Ü™™¡K*Ç ,lThe movie controller type. See ß “Object Controller Types” ¶ for a description of the available movie ¡W*Å E controllers for object views.
åC ¡fˇ÷ eviewStateCount ¢
Å%Ü™™¡v*Ä $iThe number of view states of the object. A view state selects an alternate set of images for an object’s ¡Ç* D1views. The value of this field must be positive.
åD ¡ëˇ‘ edefaultViewState ¢
Å&Ü™™¡°*~ $hThe 1-based index of the default view state. The default view state image for a given view is displayed ¡≠*} L(when the mouse button is not down. ù
åE ¡ºˇ“ emouseDownViewState ¢
Å'Ü™™¡Ã*| $aThe 1-based index of the mouse-down view state. The mouse-down view state image for a given view p¡ÿ*{ Qis displayed while the user holds the mouse button down while the cursor is over Dan object movie.
ÅÜ™™æ™ß $bThe number of frames into which the panoramic image is diced vertically. The height of each frame 0¿J™¶ Z(which is ãimageSizeY Ü/ ãimageNumFramesY Ü) should be divisible by 4. For a D@high-resolution panorama, a typical value for this field is24.
å9 ¿fˇ˙ ehotSpotSizeX ¢
ÅÜ™™¿v™§ d]The width, in pixels, of the panorama stored in the highest resolution hot spot image track.
å: ¿Üˇ˘ ehotSpotSizeY ¢
ÅÜ™™¿ñ™£ d^The height, in pixels, of the panorama stored in the highest resolution hot spot image track.
å; ¿¶ˇ¯ ehotSpotNumFramesX ¢
Å Ü™™¿∂™¢ $aThe number of frames into which the panoramic image is diced horizontally for the hot spot image ¿¬™° DLtrack. For a high-resolution panorama, a typical value for this field is 1.
å< ¿“ˇˆ ehotSpotNumFramesY ¢
Å Ü™™¿‚™† $fThe number of frames into which the panoramic image is diced vertically for the hot spot image track. ¿Ó™ü DKFor a
high-resolution panorama, a typical value for this field is 24.
å= ¿˛ˇÙ e flags ¢
Å Ü™™¡™û l^A set of panorama flags. See Í “Panorama Sample Flag” È for the currently defined flag.
å> ¡ ˇÛ ereserved1 ¢
Å Ü™™¡.™ù d Reserved. This field must be 0.
å? ¡>ˇÚ ereserved2 ¢
Å!Ü™™¡N™ú d Reserved. This field must be 0.
Z¡]™õ l" ˙ Object Sample Atom Structure
1¡i™ö ,k ë ê An object sample atom describes a single object, including information about the default viewing Wangles and the view settings. The structure of an object sample atom is defined by the L(VRObjectSampleAtom Ü data type: 4
Å*Ü™™¿N™ß $`The number of columns in the object image array (that is, the number of horizontal positions or 0¿Z™¶ Lincrements in the range defined by the minimum and maximum pan values). The L+value of this field must be positive. õ
åH ¿vˇ˙ e
rows ¢
Å+Ü™™¿Ü™§ $fThe number of rows in the object image array (that is, the number of vertical positions or increments 0¿í™£ Pin the range defined by the minimum and maximum tilt values). The value of this Dfield must be positive.
åI ¿Æˇ˜ emouseMotionScale ¢
Å,Ü™™¿æ™° $fThe mouse motion scale factor (that is, the number of degrees that an object is panned or tilted when 0¿ ™† Qthe cursor is dragged the entire width of the VR movie image). The default value Lis 180.0. ö
åJ ¿ÊˇÙ e minPan ¢
Å-Ü™™¿ˆ™û $oThe minimum pan angle, in degrees. The value of this field must be less than the value of the ãmaxPan Ü ¡™ù Dfield.
åK ¡ˇÚ e maxPan ¢
Å.Ü™™¡"™ú $aThe maximum pan angle, in degrees. The value of this field must be greater than the value of the ¡.™õ DminPan Ü field.
åL¡>ˇ edefaultPan ¢
Å/Ü™™¡N™ö $fThe default pan angle, in degrees. This is the pan angle used when the object is first displayed. The 0¡Z™ô ]value of this field must be greater than or equal to the value of the ãminPan Ü field DCand less than or equal to the value of the ãmaxPan Ü field.
åM ¡vˇÌ e
minTilt ¢
Å0Ü™™¡Ü™ó $jThe minimum tilt angle, in degrees. The default value is +90.0. The value of this field must be less than ¡í™ñ D*the value of the ãmaxTilt Ü field.
åN ¡¢ˇÎ e
maxTilt ¢
Å1Ü™™¡≤™ï $hThe maximum tilt angle, in degrees. The default value is –90.0. The value of this field must be greater ¡æ™î D/than the value of the ãminTilt Ü field.
Å3Ü™™æ™ß $hThe minimum field of view to which the object can zoom. The valid range for this field is from 1 to the ¿J™¶ DTvalue of the ãfieldOfView Ü field. The value of this field must be positive.
åQ ¿Zˇ˚ efieldOfView ¢
YÜ™™¿j™• $lThe image field of view, in degrees, for the entire object. The value in this field must be greater than or ¿v™§ L?equal to the value of the ãminFieldOfView Ü field. ò
åR ¿Üˇ˘ edefaultFieldOfView ¢
ÄOÜ™™¿ñ™£ $n The default field of view for the object. This is the field of view used when the object is first displayed. ¿¢™¢ JThe value in this field must be greater than or equal to the value of the DbminFieldOfView Ü field and less than or equal to the value of the ãfieldOfView Ü field.
åS¿æˇˆ edefaultViewCenterH ¢
ÄKÜ™™¿Œ™† l* The default horizontal view center. t
åT ¿fiˇı edefaultViewCenterV ¢
ÄMÜ™™¿Ó™ü d# The default vertical view center.
åU ¿˛ˇÙ eviewRate ¢
ÄNÄÜ™™¡™û $lThe view rate (that is, the positive or negative rate at which Üthe view animation in objects plays, if 2¡™ù Pview animation is enabled). The value of this field must be from –100.0 through L+100.0, inclusive. ó
åV ¡6ˇÒ eframeRate ¢
ÄLÄ
Ü™™¡F™õ $mThe frame rate (that is, the positive or negative rate at which Üthe frame animation in a view plays, if 2¡R™ö Qframe animation is enabled). The value of this field must be from –100.0 through L+100.0, inclusive. ñ
åW ¡nˇÓ eanimationSettings ¢
Å9Ü™™¡~™ò ,nA set of 32 bit flags that encode information about the animation settings of the object. See ñ “Animation 0¡ä™ó ZSettings” ï for a description of the constants you can use to specify a value for this L field. î
åX ¡¶ˇÎ econtrolSettings ¢
Å:Ü™™¡∂™ï ,jA set of 32 bit flags that encode information about the control settings of the object. See ô “Control p¡¬™î ZSettings” ö for a description of the constants you can use to specify a value for this L field. ï
6U¬ ¡Ô Ò M 6U¬ ¡Ô LUNNY l ¬X ¬ë h RR1 6U¬ ¡Ô i P 6U¬ ¡Ô D R* 6U¬ ¡Ô k P 6U¬ ¡Ô U QQY l ¬X ¬ë U UU2 9U¬ ¡Ô V S 9U¬ ¡Ô ¡ ˇÏ D U) Ç Ü™™Ü™™ l% ä Track Reference Entry Structure
\¿M™¶ e0Ungroup the objects and select the text column.
]¿v™§ %QConnect the two columns on the page and change the flow settings for the one you ¿k™§ EKpasted. (See the ôTucson User’s Guide Ω for specific instructions.)
k¿}™£ %QDelete any paragraphs in the column that you do not need. (See “What to Delete,” ¿â™¢ Ebelow.)
Ä ¿õ™° eLCreate cross-references in the text column to paragraphs in the first file.
á)¿Á™û eSBring the white rectangle behind the text column to the front to cover the column.
á*Ä¿≈ˇı eWhat to Delete
á+=Ü™™¿‘™ü eGIf the document uses a chapter TOC, delete the CO.Multifile paragraph.
á,¿Ê™û eKIf the document uses a chapter opener, delete the ChT.Multifile paragraph.
á-¿|UM ePIf the first page of the document has an H1, delete the H1.Multifile paragraph.
á.¿Yˇ¯ %MIf the document does not use commands formats, delete the CmH0.Multifile and ¡™õ ECmH.Multifile paragraphs.
RM -] X L+.Multiline. Apply this format to multi-line listing captions. Copy the anchored frame W Rcontaining the rule and paste it at the beginning of the listing caption. The two , E6anchored frames on this page are not interchangeable.
Ç6∞™ß $eTo play a time-based track with the object movie, you must synchronize the sample data of that track 0º™¶ hto the start and stop times of a view in the object image track. For example, to play a different sound dwith each view of an object, you might store a sound track in the movie file with each set of sound ^samples synchronized to play at the same time as the corresponding object’s view image. (This _technique also works for video samples.) Another way to add sound or video is simply to play a hsound or video track during the object’s view animation; to do this, you need to add an active track to DCthe object that is equal in duration to the object’s row duration.
ÇÄáUT¿ñUJ d Single-Node Panoramic Movies
Ç4Ü™™¿¢™û ,m ∏ Figure4-4 π illustrates the basic structure of a single-node panoramic movie. As you can see, every 0¿Æ™ù bpanoramic movie contains at least three tracks: (1)a QTVR track, (2)a panorama track, and (3)a Dpanorama image track.
Ç9¿fiˇÒ l> ª The structure of a single-node panoramic movie file Ω
Ç:Ü™™¡d™õ $WFor a single-node panoramic movie, the QTVR track contains just one sample. There is a 0¡p™ö acorresponding sample in the panorama track, whose time and duration are the same as the time and bduration of the sample in the QTVR track. The time base of the movie is used to locate the proper `video sample in the panorama image track. For a panoramic movie, the video sample for the first bdiced frame of a node’s panoramic image is located at the same time as the corresponding QTVR and apanorama track samples. The duration of all the video samples is the same as the duration of the D3corresponding QTVR sample and the panorama sample.
Ç?¡æ™î $]Like an object movie, a panoramic movie can contain an optional hot spot image track and any p¡ ™ì _number of standard QuickTime tracks. A panoramic movie can also contain panoramic image tracks gwith a lower resolution. The video samples in these low-resolution image tracks must be located at the csame time and must have the same total duration as the QTVR track. Likewise, the video samples for 9U¬ ¡Ô ] 9U¬ ¡Ô ÇSÄHÄ Ä Y l ¬X ¬ë ^ ÄHÄH 6U¬ ¡Ô _ Ä 6U¬ ¡Ô ¡‡ˇ D Ä7Ä7 ÄH
ÇA™™® $NIn a QuickTimeVR movie file, the panorama image tracks and panorama hot spot 0∂™ß Ptracks must be disabled, but the object image tracks and object hot spot tracks L'must be enabled. ¬ ˆs Ü ¡
Ç"ÄáUT¿`UO dMultinode Movies
Ç8Ü™™¿l™£ ,jA multinode QuickTimeVR movie can contain any number of object and panoramic nodes. ¿ Figure4-5 ø 0¿x™¢ `illustrates the structure of a QuickTimeVR moviethat contains five nodes (in this case, three D'panoramic nodes and two object nodes).
Ç;¿®ˇˆ l2 æ The structure of a multinode movie file º
Ç$Ü™™¡Ü™† lfPanoramic tracks and object tracks must never be located at the same time. Á ˆs Ü Ã _
Å
uä™™¡ú™ü l( Ì Using the QuickTimeVR File Format
Ö Ü™™¡≥™û ,k fl This section illustrates basic ways of using the QuickTimeVR file format. Inparticular, it provides ¡ø™ù D+source code examples that show how you can
Åk¡—™ú $^specify the QuickTimeVR movie controller by including a piece of user data in a QuickTimeVR P¡›™õ D movie file
¿ú ^¡§ ¡∂Ä = Ä@ ÇÄ ÄaÄa ÄA Ä} 6硡 Eı â[_Ä" 6硡硡â] ÄaGãCÜ™™ eN Ä} ¿ê 硡 E˜ â[Ä!àG ¿ê 硡硡â] ÄaGãCÜ™™ e Ä} ¿ê 硡 E˘ â[â2Ä$ ¿ê 硡硡â] Äb GãCÜ™™ e X:Overview Ä} H硡 E˚ â[Ä#â+ H硡硡â] ÄbGãCÜ™™ e See Also ¬X ¬ë (· Ä&Ä* 6U¬ ¡Ô (‚ Ä% Ä( 6U¬ ¡Ô Ä'Ä'
{¿S™ß SThere are two main reasons you might need to read this chapter. First, you need to 0¿_™¶ Oknow about the format of QuickTimeVR files if you want to create QuickTimeVR Umovies without the assistance of movie-authoring software, or if you want to develop Rsome QuickTimeVR movie-authoring software itself. Second, you need to know about Kthe format of QuickTimeVR files if you want to extract information from a PQuickTimeVR file that cannot be obtained using QuickTimeVR Manager functions. SFor instance, there is no QuickTimeVR Manager function that returns the name of a Tgiven node; however, you can easily get a node’s name by reading the information in @Tthe atoms in the atom container returned by the ãQTVRGetNodeInfo Ü function.
Åj¿À™û @In general, you don’t need to know about the format of atoms or 0¿◊™ù <atom containers simply to use the functions provided by the H,QuickTimeVR Manager. \ ˆu Ü ≈
'¿ı™õ OIf you want to create QuickTimeVR movies, you should already be familiar with 0¡™ö [QuickTime, as described in ôInside Macintosh: QuickTime. Ü You should be especially Vfamiliar with the sections of that book that describe how to create movies and how to Twork with media samples. If you want to directly access the movie data stored in an Ratom container, you also need to be familiar with the atom routines introduced in aQuickTime version 2.1. See ôDeveloper’s Guide: QuickTime for Macintosh, Version 2.5 Ü for @Ocomplete details on creating and managing the atoms that make up a movie file.
M¡O™î WT Üo use this chapter, you also need to be familiar with QuickTimeVR. See handlink ¡[™ì @9“About QuickTimeVR” f Üor the necessary information.
Ö#¡m™í (U O This chapter begins by briefly describing the QuickTimeVR file format. Then it 0¡y™ë Qprovides some sample code that shows how to read information from the atoms in a _QuickTimeVR movie file. The section Œ “ ÜQuickTimeVR File Format Reference Ü” Õ , Sprovides a complete reference to the constants and data structures that define the TQuickTimeVR file format. (These constants and data structures are contained in the @,header file ãQuickTimeVRFormat.h Ü.)
Ñ+¡¡™å EThis chapter describes the file format supported by version2.0 Ü p¡Õ™ã Cand later Üof the QuickTimeVR Manager. For information on the ?file format supported by earlier versions of QuickTimeVR, see ;Macintosh Technical Notes numbers 1035 and 1036 (available HLelectronically on the ôDeveloper CDSeries Ü). > ˆs Ü 4
¬X ¬ë Q ÇMÇM
6U¬ ¡Ô R Ä: 6U¬ ¡Ô ¡Îˇ€ @% % ÇM (u䙙䙙 d Contents
zÜ™™¿M™¶ ,i O A QuickTimeVR movie is stored on disk in a format known as the ÚQuickTimeVR file format. Ü 0¿Y™• cBeginning in QuickTimeVR version 2.0, a VR movie file can contain one or more nodes. Each node is deither a panorama or an object. In addition, a QuickTimeVR movie can contain links between any two Dtypes of nodes.
}¿É™¢ ,p U All QuickTimeVR movies contain a single ÚQTVR track, Ü a special type of
QuickTime track that Ä¿è™° imaintains a list of the nodes in the movie. Each individual Üsample in a QTVR track contains general " ainformation and hot spot information for a particular node. If a QuickTimeVR movie contains any apanoramic nodes, that movie also contains a single panorama track, and if it contains any object bnodes, it also contains a single object track. The panorama and object tracks contain information D3specific to the panoramas or objects in the movie.
Åi¿—™ú $cThe actual image data for both panoramas and objects is stored in standard QuickTime video tracks, 0¿›™õ nhereafter referred to as Úimage tracks. Ü The individual frames in the image track for a panorama make aup the diced frames of the original single panoramic image. The frames for the image track of an iobject represent the many different views of the object. Hot spot image data is stored in parallel video D'tracks for both panoramas and objects.
xsà™™¡%™ó d QTVR Track
ÄÜ™™¡2™ñ ,q V W As mentioned earlier, the QTVR track is a special type of QuickTime track that maintains a list of all 0¡>™ï kthe nodes in a movie. The media type for a QTVR track is ã'qtvr' Ü. All the media samples in a QTVR atrack share a common sample description, which contains the VR world atom container. The ÚVR r kworld Ü atom container includes such information as the name for the entire scene, the default node ID, D\and default imaging properties, as well as a list of the nodes contained in the QTVR track.
Å ¡z™ë $KA VR world can also contain custom scene information. QuickTimeVR ignores 0¡Ü™ê Sany atom types that it doesn’t recognize, but you can extract those atoms from the LHVR world using standard QuickTime atom functions. } ˆu Ü |
Å~¡§™é ,k Y The QTVR track contains one media sample for each node in the movie. Each sample contains a Únode r¡∞™ç ginformation atom container. Ü The node information includes general information about the node such b das the node’s type, ID, and name. The node information atom container also contains the list of hot Dspots for the node.
ÄiÜ™™¿O™¶ ,x Z P A movie’s Úpanorama track Ü is a track that contains information about the panoramic nodes in a scene. 0¿[™• m(The media type of the panorama track is ã'pano' Ü.) Each sample in a panorama track corresponds to a `single panoramic node. This sample parallels the corresponding node in the QTVR track. Panorama `tracks do not have a sample description (although QuickTime requires that you specify a “dummy” ksample description when you call ãAddMediaSample Ü to add a sample to a panorama track). The sample iitself contains the data that specifies the track reference indexes of the scene and hot spot tracks. In caddition, the sample contains information about how the panoramic image has been diced, as well as ethe viewing angle limits and default view angles for the panorama. The image and hot spot tracks for DUa panorama can be obtained using the QuickTime ãGetTrackReference Ü function.
Ç¿«™ù $DThe panorama image track is referenced by a track reference of type ¿”™ú OkQTVRImageTrackRefType Ü the hot spot image track is referenced by a track LLreference of type ãkQTVRHotSpotTrackRefType Ü. Â ˆu Ü Ê
Ç¿Ò™ö ,w b ` The actual panoramic image for a panoramic node is contained in a Úpanorama image track, Ü which is a 0¿˝™ô astandard QuickTime video track. The panoramic imagecan be created in many ways. You can use the ^stitcher provided by the QuickTimeVR Authoring Suite to stitch together several photographs. Ä DSAlternatively, you can use a graphics rendering application or a panoramiccamera.
Ån¡'™ñ ,b d æ QuickTimeVR version 2.0 requires the original panoramic image to be rotated 90degrees 0¡3™ï `counterclockwise. The rotated image must then be diced into smaller frames. Each diced frame is ecompressed and added to the video track as a video sample. (See Ö Figure4-1 Ü .) Frames can be [compressed using any spatial compressor; temporal compression is not allowed for panoramic L
movies. e
Åp¡o™ë $LA panorama sample atom (which contains information about a single panorama) p¡{™ê Mcontains a flag that indicates whether the diced panoramic image is oriented Vhorizontally or vertically. Currently, only vertical orientation is supported. Future LZversions of QuickTimeVR might support horizontal panoramic images. … ˆu Ü À
¬X ¬ë Í ÇPÇP
9U¬ ¡Ô Î Ä@ 9U¬ ¡Ô ¡øÄ @ Ä Ä Ä ÇP WÅw l1 ; Creating an image track for a panorama <
lower resolution image track, if available. A low-resolution image track Ä kcontains Üdiced frames just like the higher resolution track, but the reconstructed panoramic image is " ehalf the height and half the width of the higher resolution image. The number of diced frames in the LRlower resolution image track is usually half that in the normal image track. f
Ç¿T™§ ,{ h g When a panorama contains hot spots, the movie file contains a Úhot spot image track, Ü a video track that 0¿`™£ ccontains a parallel panorama with the hot spots designated by colored regions. Each diced frame of `the hot spot panoramic image must be compressed with a lossless compressor (such as QuickTime’s cgraphics compressor). The dimensions of the hot spot panoramic image are usually the same as those cof the image track’s panoramic image, but this is not required. The dimensions must, however, have dthe same aspect ratio as the image track’s panoramic image. A hot spot image track should be 8 bits Ddeep.
=¿¥™ù $PIn QuickTimeVR version 2.0, the panoramic images in thelower resolution image 0¿¿™ú Mtracks and the hot spot imagetracks, if present, must be rotated 90degrees Ljcounterclockwise (just like image in the panorama imagetrack). c ˆs Ü ® Q [ a c
ÄHsà™™¿™ö d
Object Track
ÄxÜ™™¿˝™ô ,x \ R A movie’s Úobject track Ü is a track that contains information about the object nodes in a scene. (The 0¡ ™ò smedia type of the object track is ã'obje' Ü.) Each sample in an object track corresponds to a single object dnode in the scene. The samples of the object track contain information describing the object images mstored in the
object image track. These object information samples parallel the corresponding Ünode fsamples in the QTVR track and are equal in time and duration with a particular object node’s hot spot hsamples in the object’s hot spot track as well as the object node’s image samples in the object’s image Dtrack.
Å|¡]™í $OIn QuickTimeVR version 2.0, all objects in a single movie must be of the same 0¡i™ë Lsize (that is, the same number of pixels high and the same number of pixels L wide). „ ˆu Ü ‰
Äw¡á™è $_Object tracks do not have a sample description (although QuickTime requires that you specify a p¡ì™é g“dummy” sample description when you call ãAddMediaSample Ü to add a sample to an object track). dCurrently, the sample itself is an atom container that contains a single object sample atom; in the cfuture, the sample might contain optional atoms describing new or private features of a particular gobject. In contrast with the panorama sample atom, track references in the object are not described in ethe object sample atom. The associated image and hot spot tracks for an object can be obtained using D4the QuickTime ãGetTrackReference Ü function.
v∞™ß ,s i The actual views of an object for an object node are contained in an Úobject image track, Ü which is a 0º™¶ estandard QuickTime video track. As described in the section Ü handlink “About QuickTimeVR/Object iNodes,” Üthese views are often captured by moving a camera around the object in a defined pattern of epan and tilt angles. The views must then be ordered into an object image array, which is stored as a LZone-dimensional sequence of frames in the movie’s video track (see Ø Figure4-2 Æ ).
Ç
¿Ñˇ¯ l8 ≠ The structure of an image track for an object ∞
Ç
Ü™™¡.™¢ $dFor object movies containing frame animation, each animated view in the object image array consists 0¡:™° gof the animating frames. It is not necessary that each view in the object image array contain the same L`number of frames, but the view duration of all views in the object movie must be the same. ¯
7¡X™ü $hFor object movies containing alternate view states, alternate view states are stored as separate object 0¡d™û dimage arrays that immediately follow the preceding view state in the object image track. Each state edoes not need to contain the same number of frames. However, the total movie time of each view state L8in an object node must be the same. ˘ S ] j
Ç sà™™¡†™õ dQuickTimeVR Movie Files
Ç>Ü™™¡≠™ö ,f ^ A QuickTimeVR movie file is a QuickTime movie file. The only differences between a QuickTimeVR p¡π™ô ^movie file and a typical time-based QuickTime movie file are the type and usage of the tracks gcontained in the movie and the necessary QuickTime user data attached to the movie. In particular, for Dxthe MacOS, the file type should be ã'MooV' Ü for Windows systems, the file extension should be ã.mov Ü.
Ç@§™® $bAlso, as with any QuickTime movie that is intended to be played on both operating systems, a data ∞™ß ^fork version of the file should be created using the ãFlattenMovie Ü function with the iflattenAddMovieToDataFork Ü flag set. Note that the resulting file is optimized for random access and D`might not perform well in an environment that requires streaming access (such as Web browsing).
Ç ÄáUT¿fUN dSingle-Node Object Movies
Ç3Ü™™¿r™¢ ,q µ Figure4-3 ∂ illustrates the basic structure of a single-node object movie. As you can see, every object ¿~™° Dlmovie contains at least three tracks: (1)a QTVR track, (2)an object track, and (3)an object image track.
Ç ¿¢ˇˆ l; ¥ The structure of a single-node object movie file ≥
Ç<Ü™™¡(UJ $bFor a single-node object movie, the QTVR track contains just one sample. There is a corresponding 0¡4UI asample in the object track, whose time and duration are the same as the time and duration of the fsample in the QTVR track. The time base of the movie is used to locate the proper video sample in the dobject image track. For an object movie, the frame corresponding to the first row and column in the cobject image array is located at the same time as the corresponding QTVR and object track samples. cThe duration of all the video samples is the same as the duration of the corresponding QTVR sample Dand the object sample.
Ç5¡ÇUC $hIn addition to these three required tracks, an object movie can also contain a hot spot image track and p¡éUB bany number of standard QuickTime tracks (such as video, sound, and text tracks). A hot spot image gtrack for an object is a QuickTime video track that contains images of colored regions delineating the dhot spots; an image in the hot spot image track must be synchronized to match the appropriate image cin the object image track. A hot spot image track should be 8 bits deep and can be compressed with D:any lossless compressor (including temporal compressors).
6U¬ ¡Ô a Ä 6U¬ ¡Ô Ä ÄKÄ Ä Y l ¬X ¬ë b ÄKÄK 9U¬ ¡Ô c ÄI 9U¬ ¡Ô ¡„ˇ⁄ D ÄK ÇEÜ™™Ü™™ d+extract a custom data atom from a VR world
Å∞™® $LThe code examples shown in this section provide only very rudimentary error º™ß L!handling. ∏ ˆu Ü π
#sà™™¿`™¶ l# ] Specifying a Movie Controller
ÄÜ™™¿m™• $cWhen you create a QuickTimeVR movie, you need to add a special piece of user data that identifies 0¿y™§ `which movie controller to invoke for this movie. The movie controller type for QuickTimeVR 2.0 jmovies is ã'qtvr' Ü. This user data is examined by the Movie Toolbox when an application calls the uNewMovieController Ü function for that movie. î Listing4-1 † shows how to add the appropriate user data to La new movie. ° £
Ä,¿¡ˇˆ l2 § Specifying the QuickTimeVR movie controller
wÜ™™¡∞™â ,i m A QuickTimeVR movie contains information describing the locations of nodes in the movie as well as ¡º™à egeneral information about the movie. This information is stored in an atom container, defined by the pQTAtomContainer Ü data structure. An Úatom container Ü is a collection of atoms. Atom containers were b ^introduced in QuickTime version 2.1, which provides a complete library of routines to extract [information from atom containers. The QuickTimeVR Manager function handlink “QuickTimeVR 9U¬ ¡Ô e ÄI 9U¬ ¡Ô ÄHÄNÄJÄJY l ¬X ¬ë f ÄNÄN 6U¬ ¡Ô g ÄL 6U¬ ¡Ô ¡¿*† D
ŧ™® $bThe VRworld includes such information as the name for the entire scene, the default node ID, and 0∞™ß ndefault imaging properties. It also contains an atom for e Üach node in the file, which describes where to Lbfind the node. Ü G Figure4-6 H is a d Üiagram of a typical VRworld atom container.
Å¿N™• l]F Üor descriptions of the atom types, see œ “ ÜVR World Atom Types Ü” ⁄ Ü.
ÄW¿f™§ ,WThe structure of a VRworld header atom is described in “ “ ÜVR World Header Atom ¿r™£ M2Structure Ü” ” . ˆu Ü ® Ü
Å¿ñˇ¯ l< ≠ Structure of ó t óhe VRWorld atom container Ø
Å Ü™™¡ò’N $\D Üuring the authoring process, you can add custom atoms to the VR world atom container. p¡§’M bQuickTimeVR ignores these custom atoms, but they can be extracted using the atom functions by an kapplication that knows how to use the information. For example, ≤ Listing4-2 ≥ extracts some custom E\data of type ã'PREF' Ü from the VR world atom container and copies it into a handle.
6U¬ ¡Ô i ÄL 6U¬ ¡Ô ÄKÄQÄMÄMY l ¬X ¬ë j ÄQÄQ 9U¬ ¡Ô k ÄO 9U¬ ¡Ô ¡—ˇ» D" " ÄQ
Åm l. – Extracting a custom atom from a VR world
Ç+ ÖUTöUT %0Handle MyGetPREFData (QTVRInstance theInstance) 0¶UR { (QTAtomContainertheVRWorld; $OSErrtheErr; %QTAtomtheAtom; -HandletheHandle = nil; //Get the VR world. 7theErr = QTVRGetVRWorld(theInstance, &theVRWorld); if (theErr == noErr) { 6//Get the atom of type 'PREF' with atom ID 1. GtheAtom = QTFindChildByID(theVRWorld, kParentAtomIsContainer, I'PREF', 1, nil); if (theAtom != 0) { G//Allocate a relocatable block and copy atom data into it. BtheHandle = NewHandleClear(sizeof(MyPREFDataStruct)); DQTCopyAtomDataToHandle(theVRWorld, theAtom, theHandle);
} ,QTDisposeAtomContainer(theVRWorld); } B//Return the handle to the caller; caller must dispose of it. return(theHandle); E}
ÇDÜ™™¡;™| ,y x See ôDeveloper’s Guide: QuickTime for Macintosh, Version 2.5 Ü œ for information about the QuickTime atom ¡G™{ Lrfunctions ÒQTFindChildByID Ü, ÒQTCopyAtomDataToHandle Ü, and ÒQTDisposeAtomContainer Ü. n
Ç'sà™™¡g™z dGetting Node Information
Å5Ü™™¡t™y ,\ ’ The QuickTimeVR Manager function Ü handlink “QuickTimeVR Manager/QTVRGetNodeInfo” 0¡Ä™x ereturns the node information atom container that describes a node and all the hot spots in the node. jOne of the atoms in a node information atom container is a Únode header atom, Ü which contains the DOtype and ID of the node, as well as the node ìname and any node comments.
Å6¡™™u l[ ‘ Figure4-7 · is a Ü d Üiagram of a typical node information atom container.
ÅW¡¬™t ,ZThe structure of Üa Ü node header atom is described in ‚ “ ÜNode Header Atom P¡Œ™s M,Structure Ü” o . ¥ ˆu Ü ∂
9U¬ ¡Ô m ÄO 9U¬ ¡Ô ÄNÄZÄPÄPY
l ¬X ¬ë n ÄZÄZ 6U¬ ¡Ô o ÄR 6U¬ ¡Ô ¡Èˇ„ D ÅÅ ÄZ Å lF ∑ ∫ Struct óu óre of the node information atom container
ÅtÜ™™¿Ê™∞ ,y “ ìY ìou can use standard QuickTime atom container Üfunctions to retrieve the information in a node header 2¿Ú™Ø uatom. For example, the ãMyGetNodeName Ü function defined in ÿ Listing4-3 Ÿ returns the name of a node, M given its node ID. T q
Ç.¡ l ™ Getting a node’s name
i ÖUT¡3UW %BOSErr MyGetNodeName (QTVRInstance theInstance, UInt32 theNodeID, p¡?UU XStringPtr theStringPtr) { ,OSErrtheErr = noErr; )QTAtomContainertheNodeInfo; +VRNodeHeaderAtomPtr theNodeHeader; 3QTAtomtheNodeHeaderAtom = 0; ///Get the node information atom container. DtheErr = QTVRGetNodeInfo(theInstance, theNodeID, &theNodeInfo); !//Get the node header atom. if (!theErr) RtheNodeHeaderAtom = QTFindChildByID(theNodeInfo, kParentAtomIsContainer, VkQTVRNodeHeaderAtomType, 1, nil); "if (theNodeHeaderAtom != 0) { ¬X ¬ë (ı ÄUÄY 9±¿ ¡¬ ¬ (ˆ ÄT ÄW 9±¿ ¡¬ ¬ ÄVÄV l 9±¿ ¡¬ ¬ (˜ ÄT 9±¿ ¡¬ ¬ ⡡ ÄU WÄJÜ™™Ü™™ e 9 ¡¬ âÄ (¯ ÄTÄUÄY 9 ¡¬ âÄ ÄXÄX l 9 ¡¬ âÄ (˘ ÄT 9 ¡¬ âÄ Üˇˇ ÄW WÄTyÑ™™Ñ™™ ` {¬f¿ ¡Ä (˙ ÄTÄW {¬f¿ ¡Ä ÄeÄe l 6U¬ ¡Ô q ÄR 6U¬ ¡Ô ÄQÄ]ÄSÄSY l ¬X ¬ë r Ä]Ä] 9U¬ ¡Ô s Ä[ 9U¬ ¡Ô ¡Áˇ∂ D' ' Ä] i ÖUTÖUT &QTLockContainer(theNodeInfo); 0ëUR 6//Get a pointer to the node header atom data. HtheErr = QTGetAtomDataPtr(theNodeInfo, theNodeHeaderAtom, nil, T(Ptr *)&theNodeHeader); '//See if there is a name atom. 9if (!theErr && theNodeHeader->nameAtomID != 0) { QTAtom theNameAtom; PtheNameAtom = QTFindChildByID(theNodeInfo, kParentAtomIsContainer, VkQTVRStringAtomType, theNodeHeader->nameAtomID, nil); $if (theNameAtom != 0) { 2VRStringAtomPtr theStringAtomPtr; P//Get a pointer to the name atom data; copy it into the string. JtheErr = QTGetAtomDataPtr(theNodeInfo, theNameAtom, nil, W(Ptr *)&theStringAtomPtr); if (!theErr) { Cshort theLen = theStringAtomPtr->stringLength; &if (theLen > 255) &theLen = 255; SBlockMove(theStringAtomPtr->string, &theStringPtr[1], theLen); .theStringPtr[0] = theLen; } }
function defined in ‹ Listing4-3 € retrieves the node information atom container (by ¡í™k wcalling
QTVRGetNodeInfo
) and then looks inside that container Üfor a node header atom with atom ID 1. If " iit finds one, it locks the container and then gets a pointer to the node header atom data. The format of DGthis data is defined by the ãVRNodeHeaderAtom Ü data structure:
l ¬X ¬ë v Ä`Ä` 6U¬ ¡Ô w Ä^ 6U¬ ¡Ô ¡Àˇœ D Ä` ÇG ÖUTÖUT 0QTAtomIDnodeID; 0ëUR 4QTAtomIDnameAtomID; 7QTAtomIDcommentAtomID; 3UInt32reserved1; 3UInt32reserved2; E*} VRNodeHeaderAtom, *VRNodeHeaderAtomPtr;
Ç-Ü™™¿Z™û $fThe desired information, the node name, is contained in the string atom whose atom ID is specified by ¿f™ù othe ãnameAtomID Ü field of this structure. Accordingly, the ãMyGetNodeName Ü function then calls " uQTFindChildByID Ü once again to find that string atom. If the string atom is found, ãMyGetNodeName Ü calls DbQTGetAtomDataPtr Ü to get a pointer to the string atom data. A string atom has this structure:
Ç/Ü™™¿fi™ê ,v s Finally, ãMyGetNodeName Ü copies the string data into the appropriate location and cleans up after itself ¿Í™è L before returning. H p
ÖDuä™™¡ ™é l( ‰ QuickTimeVR File Format Reference
ãrÜ™™¡™ç $eThis section describes the constants and data structures defined by QuickTimeVR that you can use to ¡#™å D)read and write QuickTimeVR movie files.
Ä¡5™ã d
Constants
Ä¡@™ä ,c ó This section describes the constants that you can use to specify atom types or other kinds of ¡L™â D information in a QTVR movie.
¡^™à l fi VR World Atom Types
1Ä¡j™á ,f r QuickTimeVR defines a number of types of atoms that can be contained in a VR world. You can use D1these constants to specify a VR world atom type:
¿àŸ¿t3 'Zü Å ¿àŸ¿t3n¬‰ <c>QTVR L-y (PanoSample)0001FRAMEPSFMACP0001 ¿€UV^¡a™™¿Ω 'O ÄR ≠ ÅÅ ÄSÇ
¡Aˇ§¡2Ê '\ü Å ¡Aˇ§¡2Ê7¬fl <c>QTVR L-z (NodeInfo2)0001FRAMEPSFMACP0001 ¬ ¬ë 'f Å Å = HH¡∞ ¬à 'g Å HH¡∞ ¬à ¿ŒˇÛ Å ÅvÜ™™ mA ‹ * è** Is this the right place for this diagram? *** ›
Ç -W Ÿ *** Description of the object-imaging atom is missing. Can I use the one from the ≠™ß M+old documentation I got from Tim? *** ⁄
Ç -g ÷ * è** I’ve added the entry for å'imob' è from the reference section, but I don’t have a ¡™ê ed èescription or structure for it. Can I use the structure from the old èd èocumentation I ¡.UA Mgot from Tim? *** ◊
ÅD -N ” * ï** In the diagram, please note the question about the ID value for ¡™Ø E,QTVRHotSpotAtom. Is it the hot spot ID? ***
Å`¡™Æ %e* ï** This diagram uses actual names as they appear in the header file. If that’s OK, ïI ï ¡ ™≠ MCneed to modify figures 4-6 and 4-8 to work that way, too. *** ‘
Ç m( – *** Should be 3.0 ? *** Ü —
Ç -f Õ *** èC èomment from developer -- this sample comes out byte reversed with èM èSVC. ¿r™ü MCan we fix this? *** Œ
WÅ{"ˇ˛’ˇŒ e HH¡∞ ¬à 'i Å HH¡∞ ¬à ÅÅ l Ä}¡ ¿aˇ˛¿ê 6 )C ÄuÅÅ ¡ ¿aˇ˛¿ê 6硡Äw WÅ}CÜ™™à™™ a Ä}$¿oˇ˝l0 )E ÄuÅ
Å $¿oˇ˝l0硡Äw WÇCÜ™™à™™ e1 Ä}¿ê ¿oˇ˝¿ê 0 )G ÄuÅ Å
X:Appendix," Ä} H硡 F â[â.â0 H硡硡â] ÄcGãCÜ™™ e See Also Ä} 6硡 F â[â/â1 6硡硡â] ÄcGã CÜ™™ eN Ä} 6硡 F â[â0â2 6硡硡â] ÄcGã CÜ™™ eN Ä} ¿ê 硡 F â[â1Ä# ¿ê 硡硡â] ÄcGã CÜ™™ e Ä} ¿ê •ˇ˝ F
â[â<â4 ¿ê •ˇ˝çˇˇâ] Äd Gã CÜ™™ eP:XTb.Restart Ä} H•ˇ˝ F â[â3â5 H•ˇ˝•ˇ˝â] Ädã CÜ™™ eLI
ç5 e Parent = OL
Aç6 e
Depth = 0 Ä} 6•ˇ˝ F â[â4â6 6•ˇ˝çˇˇâ] ÄdGã!CÜ™™ eN Ä} 6•ˇ˝ F â[â5â7 6•ˇ˝çˇˇâ] ÄdGã"CÜ™™ eN Ä} ¿ê •ˇ˝ F â[â6â. ¿ê •ˇ˝çˇˇâ] ÄdGã#CÜ™™ e Ä} ¿ê 硡 F â[âAâ9 ¿ê 硡硡â] Äe Gã$CÜ™™ eP:XR.RightFtr Ä} H硡 F â[â8â: H硡硡â] ÄeGã%CÜ™™ eP Ä} 6硡 F â[â9â; 6硡硡â] ÄeGå\CÜ™™ eN Ä} 6硡 F â[â:â< 6硡硡â] ÄeGå]CÜ™™ eN Ä} ¿ê 硡 F â[â;â3 ¿ê 硡硡â] ÄeGå^CÜ™™ e Ä} ¿ê •ˇ˝ F! â[âFâ> ¿ê •ˇ˝çˇˇâ] Äf Gå_CÜ™™ eP:XList.Restart Ä} H•ˇ˝ F# â[â=â? H•ˇ˝•ˇ˝â] Äfå`CÜ™™ eLI
ç3 e Parent = OL
Aç4 e
Depth = 0 Ä} 6•ˇ˝ F% â[â>â@ 6•ˇ˝çˇˇâ] ÄfGåaCÜ™™ eN Ä} 6•ˇ˝ F' â[â?âA 6•ˇ˝çˇˇâ] ÄfGåbCÜ™™ eN Ä} ¿ê •ˇ˝ F) â[â@â8 ¿ê •ˇ˝çˇˇâ] ÄfGåcCÜ™™ e Ä} ¿ê 硡 F+ â[âfâC ¿ê 硡硡â] Äg GådCÜ™™ e
P:XL.LeftFtr Ä} H硡 F- â[âBâD H硡硡â] ÄgGåeCÜ™™ eP Ä} 6硡 F/ â[âCâE 6硡硡â] ÄgGåfCÜ™™ eN Ä} 6硡 F1 â[âDâF 6硡硡â] ÄgGågCÜ™™ eN Ä} ¿ê 硡 F3 â[âEâ= ¿ê 硡硡â] ÄgGåhCÜ™™ e Ä} ¿ê •ˇ˝ F5 â[âkâH ¿ê •ˇ˝çˇˇâ] Äh GåiCÜ™™ eP:XFg.Restart Ä} H•ˇ˝ F7 â[âGâd H•ˇ˝•ˇ˝â] ÄhåjCÜ™™ eLI
Å ¿ú DD.DefinitionDef Fd.FieldDesc. ¿ú B ÇÄ ÇÄ Ä@ ÄÄ Äô
Å ¿ú DD.DefinitionDef . ¿ú B Ä@ ÄÄ Äô @
Å ¿ú DD.DefinitionDef Fd.FieldDesc. ¿ú B
Ä@ ÄÄ Äô @
Å ¿ú DD.DefinitionDef Fd.FieldDesc. BB Ä@ ÄÄ Äô
Å H1.Heading1TOC . LL Ä@ ÄÄ Äô
Å H2.Heading2TOC . VV Ä@ ÄÄ Äô
Å H3.Heading3TOC . LL Ä@ ÄÄ Äô
Å RH2.RoutineHd2TOC . VV Ä@ ÄÄ Äô
Å RH3.RoutineHd3TOC . NB Ä@ ÄÄ Äô
Å N .
B1.Bullet1 B1 . Ä@ ÄÄ Äô @ Å B
XL.LeftFtr
XDL.DraftLeft. ¿Ñ B Ä@ ÄÄ Äô L Q Å A¿Ñ L.Listing boldL:Listing< ><n+> Cv.Code. ¿Ñ B Ä@ ÄÄ Äô L Q Å A¿Ñ L.Listing boldL:Listing< ><n+> Cv.Code. Ä@ ÄÄ Äô ÄP ˇˇˇ˙‚ Å H1.Heading1 Invisible T1.Text1. VV Ä@ ÄÄ Äô C ÄQ
Å ? RH2.RoutineHd2 InvisibleC:<n>T1.Text1. ¿Ü B Ä@ ÄÄ Äô L Q Å ¿Ü L+.Multiline fignumL:Listing < ><n+> Cv.Code. BB Ä@ ÄÄ Äô @ Äs3 Å y X1Hd.TopHdr X2Hd.BtmHdr. ¿Ñ B Ä@ ÄÄ Äô F A Å A¿Ñ Fg.Figure boldF:Figure< ><n+> T1.Text1. ¿Ñ B Ä@ ÄÄ Äô F A Å A¿Ñ
TbT2.TblText2. Ä@ ÄÄ Äô T Å XTb.Restart T:Table <n+>-<n=0> . ˇˇˇ˙‚ Å Invisible
Å è˛˛˛ è˛˛˛ fignum
Å Å Invisible
Å è˛˛˛ ˇˇˇ˙‚ Å Invisible
ˇˇˇ˝q Å Invisible cv cv Å è˛˛˛
Å Å è˛˛˛ Å Invisible
ˇˇˇ˛π Å
Å B1
ˇˇˇ˛π Å Å
Å italics ˜Û† è˛˛˛ fignum ˜Û†
è˛˛˛ 8bat ˇˇˇ˙‚ Å è˛˛˛ ˜Û†
è˛˛˛ 8batcolor ˜Û†
Å è˛˛˛ B1 Å
˜Û†
è˛˛˛ 10bat Ä è˛˛˛ EquationVariables ˜Û†
Å@ è˛˛˛ B2 è˛˛˛ fignum Ä Å è˛˛˛ bold ˜Û† Å è˛˛˛ IMPORTANT
˜Û† Å è˛˛˛ Folio Ä@ ˜Û† Å è˛˛˛ WARNING Ä Å è˛˛˛ Invisible Ä Å è˛˛˛ italics ˜Û† Å è˛˛˛
Note&FdHds † Å è˛˛˛ Subscript † Å è˛˛˛ Superscript Å è˛˛˛ Ä Ä Å è˛˛˛ symbol ˜Û† Å è˛˛˛ TblNote Äs3 Å è˛˛˛
Å ˇÛ‡ è˛˛˛ cv
Å Invisible ÄÃÃ Å è˛˛˛ Å bold
Folio
è˛˛˛
Å bold
ˇˇˇ˝q Å ˇˇˇ˙‚ Å
8bat
ˇˇˇ˛6 Å ˇˇˇ˛6 cv Äs3 Å Å ˇˇˇ˙‚ Å Å
ˇˇˇˇ} Å
ˇˇˇˇ} cv
ˇˇˇ˛w Å ˇˇˇ˛w cv
ˇˇˇ˝Ù Å
ˇˇˇˇø Å ÄÃà Å
ˇˇˇ¸Ó Å
ˇˇˇ˛˙ Å Å
ˇˇˇˇ< Å ˇˇˇˇ< cv
ˇˇˇ˛π Å ˇˇˇ˛˙ cv Å
Note&FdHds Å
10bat Ä@ Å WARNING ÄÄ Å Å IMPORTANT ˇˇˇˇ ˇˇˇˇ ÄÄ ˇˇˇˇ ˇˇˇˇ Ä@ ˇˇˇˇ ˇˇˇˇ Ä33 ˇˇˇˇ ó Zˇˇˇˇ ˇˇˇˇ Ä@ ó Zˇˇˇˇ Ä@ ã Zˇˇˇˇ C ó Zˇˇˇˇ ó Zˇˇˇˇ ÄÄ Thin Medium ÄÄ Double Thick Ä@ Very Thin ˇˇÏ J ßæcJJJ ¡F JJJ SumGlblVars $ H
Ä ` d@ ˇˇˇˇ Black T!ˇˇˇˇ White dd Aˇˇˇˇ Red dd Åˇˇˇˇ Green d d ˇˇˇˇ Blue d ˇˇˇˇ Cyan d ˇˇˇˇ Magenta d ˇˇˇˇ Yellow dâˇƒ¿Yˇÿ ˇˇˇˇ Dark Blue d¿EˇÏ ˇˇˇˇ
Orange Red ¿Tˇƒ ¿Fˇ» ˇˇˇˇ Color 1 Header/Footer $1Header/Footer $1Header/Footer $2Header/Footer $2IndexIndexCommentCommentSubjectSubjectAuthorAuthorGlossaryGlossaryEquationEquation Hypertext Hypertext Cross-Ref Cross-Ref
